Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
501-tree-1
name
1600
tree-preservation-order

undefined

501-tpo-1
uprn
address-text
point
POINT (-1.037120 50.886506)
geometry
MULTIPOLYGON (((-1.037034 50.886497,-1.037038 50.886514,-1.037050 50.886529,-1.037069 50.886541,-1.037092 50.886549,-1.037119 50.886552,-1.037145 50.886550,-1.037169 50.886542,-1.037188 50.886530,-1.037200 50.886515,-1.037205 50.886499,-1.037201 50.886482,-1.037189 50.886467,-1.037171 50.886455,-1.037147 50.886447,-1.037121 50.886444,-1.037094 50.886447,-1.037070 50.886454,-1.037051 50.886466,-1.037039 50.886481,-1.037034 50.886497)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL